Skip to content

feat: upgrade middleware to use AWS SDK v3 #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 10, 2025

Conversation

alexmarqs
Copy link
Member

@alexmarqs alexmarqs commented Apr 9, 2025

Migrate to aws-sdk v3.

Let's create a RC release so we can do some more tests.

@alexmarqs alexmarqs requested a review from jpinho April 9, 2025 12:25
@alexmarqs alexmarqs marked this pull request as ready for review April 9, 2025 13:16
Copy link
Member

@jpinho jpinho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome job!

@alexmarqs
Copy link
Member Author

alexmarqs commented Apr 9, 2025

🧪 @epilot/large-response-middleware@1.0.0-rc.2 (did a few more improvements in terms of peer deps versioning)

@alexmarqs
Copy link
Member Author

I will merge to main, this is just RC's version(s) anyway + we make our work visible to community. With this I think we can start checking the Template Variables API to fully move to aws-sdk v3.

@alexmarqs alexmarqs merged commit db6a083 into epilot-dev:main Apr 10, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants